Managing projects in a content management system

ABSTRACT

Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects in a content management system. For example, the content management system can create a project folder (e.g., shared folder) for managing data associated with a project. The project folder can be shared with content management system users (e.g., project members) who are contributors to the project. The content management system can store project data (e.g., content items, communications, comments, tasks, etc.) related to the project in the project folder. When the project folder is selected by a user, the content management system can generate a project folder view that presents the project data associated with the project folder and/or project in a convenient and easy to access graphical user interface. The content management system can aggregate project data from various content items associated with the project and present the project data in a single graphical user interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. application Ser. No. 15/395,220, filedDec. 30, 2016, the content of which is hereby incorporated by referencein its entirety.

BACKGROUND

There are many software applications that assist users in managingprojects. Often these software applications are complicated anddifficult to use. Many times several different software applications arerequired to manage the various tasks, documents types, schedules,communications, and other project related activities and files. Usingthese existing systems to manage a project can be difficult to learn,burdensome to use, and time consuming for the user.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for managing projects in a content management system. Forexample, the content management system can create a project folder(e.g., shared folder) for managing data associated with a project. Theproject folder can be shared with content management system users (e.g.,project members) who are contributors to the project. The contentmanagement system can store project data (e.g., content items,communications, comments, tasks, etc.) related to the project in theproject folder. When the project folder is selected by a user, thecontent management system can generate a project folder view thatpresents the project data associated with the project folder and/orproject in a convenient and easy to access graphical user interface. Thecontent management system can aggregate project data from variouscontent items associated with the project and present the project datain a single graphical user interface.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for managing tasks in a content management system. Forexample, the content management system can collect, aggregate, and/orstore task data assigned to a user from across projects and/or contentitems. The user can select to view tasks for a particular project and/orfrom across all projects. The content management system can generate asingle graphical user interface for presenting the task data associatedwith the user. The content management system can generate a graphicaluser interface the allows the user to move tasks from one task statusgraphical element (e.g., task status container) to another task statusgraphical element to change the status of a task associated with theuser. Thus, the user can quickly and easily view the tasks assigned tothe user and update the status of tasks in an easy to use graphical userinterface.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the disclosurewill become apparent by reference to specific embodiments thereof whichare illustrated in the appended drawings. Understanding that thesedrawings depict only example embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 shows an example configuration of devices and a network inaccordance with some embodiments;

FIG. 2 is a block diagram of an example system for managing project datain a content management system;

FIG. 3 illustrates an example graphical user interface for presentingproject folders;

FIG. 4 illustrates an example graphical user interface for presenting aproject folder view;

FIG. 5 illustrates an example graphical user interface for adding a newcontent item to a project;

FIG. 6 illustrates an example graphical user interface for presenting aview of a content item added to the selected project folder;

FIG. 7 illustrates an example text that includes special expressions;

FIG. 8 illustrates an example graphical user interface presenting acontent item that was added to the selected project folder;

FIG. 9 illustrates an example graphical user interface for presenting adescription of the selected project;

FIG. 10 illustrates an example graphical user interface for presentingtasks associated with the selected project;

FIG. 11 illustrates an example graphical user interface for presentingtagged project data;

FIG. 12 illustrates an example graphical user interface for presentingcomments associated with a project;

FIG. 13 illustrates an example graphical user interface presentingrecently accessed content items;

FIG. 14 illustrates an example graphical user interface for presentingtasks associated with a particular user of a content management system;

FIG. 15 illustrates an example graphical user interface for creating anew task;

FIG. 16 illustrates an example graphical user interface presenting anewly created task;

FIG. 17 illustrates an example graphical user interface presenting acolumn view of tasks associated with the user;

FIG. 18 illustrates an example graphical interface for changing thestate of a task;

FIG. 19 is an example process for managing projects in a contentmanagement system;

FIG. 20 is an example process for managing tasks in content managementsystem;

FIG. 21A shows an example possible system embodiment for implementingvarious embodiments of the present technology; and

FIG. 21B shows an example possible system embodiment for implementingvarious embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses the need in the art for an easy,simple, and convenient way for users to manage project data. Byorganizing project data into a shared project folder managed by thecontent management system described herein, users are able to access allproject data for a specific project at a single location. Moreover, thecontent management system can generate and present project data bygenerating a graphical user interface that aggregates project data fromacross content items stored in the shared folder and/or associated withthe project so that the user does not have to run multiple softwareapplications or interact with multiple user interfaces to view theproject data. Additionally, since the content management systemsynchronizes the project folder with the computing devices associatedwith members/users of the project, project members can access projectdata through the content management system's servers or on the localfile system of the users' devices (e.g., when the user's device is notconnected to the network). The technology disclosed herein improves theefficiency of both user device and content management system serverdevices by reducing the number of software applications a userpreviously had to install on the user's device to perform projectmanagement tasks. Moreover, by storing all project data in a centralizedlocation (e.g., instead of at different locations), the user deviceand/or the content management system servers are required to do lessprocessing to find, aggregate, process, and present data (e.g., contentitems, comments, tasks, etc.) associated with a project.

With respect to implementing various embodiments of the disclosedtechnology, an example system configuration 100 is shown in FIG. 1,wherein electronic devices communicate via a network for purposes ofexchanging content and other data. The system can be configured for useon a wide area network such as that illustrated in FIG. 1. However, thepresent principles are applicable to a wide variety of networkconfigurations that facilitate the intercommunication of electronicdevices. For example, each of the components of system 100 in FIG. 1 canbe implemented in a localized or distributed fashion in a network.

In system 100, a user can interact with content management system 106(e.g., an online synchronized content management system) through clientdevices 102 ₁, 102 ₂, . . . , 102 _(n) (collectively “102”) connected tonetwork 104 by direct and/or indirect communication. Content managementsystem 106 can include a single computing device (e.g., a server) ormultiple computing devices (e.g., multiple servers) that are configuredto perform the functions and/or operations necessary to provide theservices described herein. Content management system 106 can supportconnections from a variety of different client devices, such as: desktopcomputers; mobile computers; mobile communications devices, e.g. mobilephones, smart phones, tablets; smart televisions; set-top boxes; and/orany other network enabled computing devices. Client devices 102 can beof varying type, capabilities, operating systems, etc. Furthermore,content management system 106 can concurrently accept connections fromand interact with multiple client devices 102.

A user can interact with content management system 106 via a client-sideapplication installed on client device 102 _(i). In some embodiments,the client-side application can include a content management systemspecific component. For example, the component can be a stand-aloneapplication, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 106 via a third-party application, such as a web browser, thatresides on client device 102 _(i) and is configured to communicate withcontent management system 106. In either case, the client-sideapplication can present a user interface (UI) for the user to interactwith content management system 106. For example, the user can interactwith the content management system 106 via a client-side applicationintegrated with the file system or via a webpage displayed using a webbrowser application.

Content management system 106 can enable a user to store content items,as well as perform a variety of content management tasks, such asretrieve, modify, browse, and/or share the content items. Furthermore,content management system 106 can enable a user to access the contentfrom multiple client devices 102. For example, client device 102 _(i)can upload content to content management system 106 via network 104.Later, the same client device 102 _(i) or some other client device 102_(j) can retrieve the content from content management system 106.

To facilitate the various content management services, a user can createan account with content management system 106. User account database 150can maintain the account information. User account database 150 canstore profile information for registered users. In some cases, the onlypersonal information in the user profile can be a username and/or emailaddress. However, content management system 106 can also be configuredto accept additional user information such as birthday, address, billinginformation, etc.

User account database 150 can include account management information,such as account type (e.g. free or paid), usage information, (e.g. fileedit history), maximum storage space authorized, storage space used,content storage locations, security settings, personal configurationsettings, content sharing data, etc. Account management module 124 canbe configured to update and/or obtain user account details in useraccount database 150. The account management module 124 can beconfigured to interact with any number of other modules in contentmanagement system 106.

An account can be used to store content items, such as digital data,documents, text files, audio files, video files, etc., from one or moreclient devices 102 authorized on the account. The content items can alsoinclude collections for grouping content items together with differentbehaviors, such as folders, playlists, albums, etc. For example, anaccount can include a public folder that is accessible to any user. Thepublic folder can be assigned a web-accessible address. A link to theweb-accessible address can be used to access the contents of the publicfolder. In another example, an account can include: a photos collectionthat is intended for photos and that provides specific attributes andactions tailored for photos; an audio collection that provides theability to play back audio files and perform other audio relatedactions; or other special purpose collection. An account can alsoinclude shared collections or group collections that are linked with andavailable to multiple user accounts. The permissions for multiple usersmay be different for a shared collection.

The content items can be stored in content storage 160. Content storage160 can be a storage device, multiple storage devices, or a server.Alternatively, content storage 160 can be a cloud storage provider ornetwork storage accessible via one or more communications networks.Content management system 106 can hide the complexity and details fromclient devices 102 so that client devices 102 do not need to knowexactly where or how the content items are being stored by contentmanagement system 106. In some embodiments, content management system106 can store the content items in the same collection hierarchy as theyappear on client device 102 _(i). However, content management system 106can store the content items in its own order, arrangement, or hierarchy.Content management system 106 can store the content items in a networkaccessible storage (NAS) device, in a redundant array of independentdisks (RAID), etc. Content storage 160 can store content items using oneor more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4,HFS/HFS+, BTRFS, and so forth.

Content storage 160 can also store metadata describing content items,content item types, and the relationship of content items to variousaccounts, collections, or groups. The metadata for a content item can bestored as part of the content item or can be stored separately. In onevariation, each content item stored in content storage 160 can beassigned a system-wide unique identifier.

Content storage 160 can decrease the amount of storage space required byidentifying duplicate content items or duplicate segments of contentitems. Instead of storing multiple copies, content storage 160 can storea single copy and then use a pointer or other mechanism to link theduplicates to the single copy. Similarly, content storage 160 can storecontent items more efficiently, as well as provide the ability to undooperations, by using a content item version control that tracks changesto content items, different versions of content items (includingdiverging version trees), and a change history. The change history caninclude a set of changes that, when applied to the original content itemversion, produce the changed content item version.

Content management system 106 can be configured to support automaticsynchronization of content items from one or more client devices 102.The synchronization can be platform agnostic. That is, the content itemscan be synchronized across multiple client devices 102 of varying type,capabilities, operating systems, etc. For example, client device 102_(i) can include client software, which synchronizes, via asynchronization module 132 at content management system 106, content inclient device 102 _(i)'s file system with the content in an associateduser account. In some cases, the client software can synchronize anychanges to content in a designated collection and its sub-collections,such as new, deleted, modified, copied, or moved content items orcollections. The client software can be a separate software application,can integrate with an existing content management application in theoperating system, or some combination thereof. In one example of clientsoftware that integrates with an existing content managementapplication, a user can manipulate content items directly in a localcollection, while a background process monitors the local collection forchanges and synchronizes those changes to content management system 106.Conversely, the background process can identify content items that havebeen updated at content management system 106 and synchronize thosechanges to the local collection. The client software can providenotifications of synchronization operations, and can provide indicationsof content statuses directly within the content management application.Sometimes client device 102 _(i) may not have a network connectionavailable. In this scenario, the client software can monitor the linkedcollection for content item changes and queue those changes for latersynchronization to content management system 106 when a networkconnection is available. Similarly, a user can manually start, stop,pause, or resume synchronization with content management system 106.

A user can view or manipulate content via a web interface generated andserved by user interface module 122. For example, the user can navigatein a web browser to a web address provided by content management system106. Changes or updates to content in the content storage 160 madethrough the web interface, such as uploading a new version of a contentitem, can be propagated back to other client devices 102 associated withthe user's account. For example, multiple client devices 102, each withtheir own client software, can be associated with a single account andcontent items in the account can be synchronized between each of themultiple client devices 102.

Content management system 106 can include a communications interface 120for interfacing with various client devices 102, and can interact withother content and/or service providers 109 ₁, 109 ₂, . . . , 109 _(n)(collectively “109”) via an Application Program Interface (API). Certainsoftware applications can access content storage 160 via an API onbehalf of a user. For example, a software package, such as an apprunning on a smartphone or tablet computing device, can programmaticallymake calls directly to content management system 106, when a userprovides credentials, to read, write, create, delete, share, orotherwise manipulate content. Similarly, the API can allow users toaccess all or part of content storage 160 through a web site.

Content management system 106 can also include authenticator module 126,which can verify user credentials, security tokens, API calls, specificclient devices, and so forth, to ensure only authorized clients andusers can access content items. Further, content management system 106can include analytics module 134 module that can track and report onaggregate file operations, user actions, network usage, total storagespace used, as well as other technology, usage, or business metrics. Aprivacy and/or security policy can prevent unauthorized access to userdata stored with content management system 106.

Content management system 106 can include sharing module 130 formanaging sharing content publicly or privately. Sharing content publiclycan include making the content item accessible from any computing devicein network communication with content management system 106. Sharingcontent privately can include linking a content item in content storage160 with two or more user accounts so that each user account has accessto the content item. The sharing can be performed in a platform agnosticmanner. That is, the content can be shared across multiple clientdevices 102 of varying type, capabilities, operating systems, etc. Thecontent can also be shared across varying types of user accounts.

In some embodiments, content management system 106 can be configured tomaintain a content directory identifying the location of each contentitem in content storage 160. The content directory can include a uniquecontent entry for each content item stored in the content storage.

A content entry can include a content path that can be used to identifythe location of the content item in a content management system. Forexample, the content path can include the name of the content item and afolder hierarchy associated with the content item. For example, thecontent path can include a folder or path of folders in which thecontent item is placed as well as the name of the content item. Contentmanagement system 106 can use the content path to present the contentitems in the appropriate folder hierarchy.

A content entry can also include a content pointer that identifies thelocation of the content item in content storage 160. For example, thecontent pointer can include the exact storage address of the contentitem in memory. In some embodiments, the content pointer can point tomultiple locations, each of which contains a portion of the contentitem.

In addition to a content path and content pointer, a content entry canalso include a user account identifier that identifies the user accountthat has access to the content item. In some embodiments, multiple useraccount identifiers can be associated with a single content entryindicating that the content item has shared access by the multiple useraccounts.

To share a content item privately, sharing module 130 can be configuredto add a user account identifier to the content entry associated withthe content item, thus granting the added user account access to thecontent item. Sharing module 130 can also be configured to remove useraccount identifiers from a content entry to restrict a user account'saccess to the content item.

To share content publicly, sharing module 130 can be configured togenerate a custom network address, such as a uniform resource locator(URL), which allows any web browser to access the content in contentmanagement system 106 without any authentication. To accomplish this,sharing module 130 can be configured to include content identificationdata in the generated URL, which can later be used to properly identifyand return the requested content item. For example, sharing module 130can be configured to include the user account identifier and the contentpath in the generated URL. Upon selection of the URL, the contentidentification data included in the URL can be transmitted to contentmanagement system 106 which can use the received content identificationdata to identify the appropriate content entry and return the contentitem associated with the content entry.

In addition to generating the URL, sharing module 130 can also beconfigured to record that a URL to the content item has been created. Insome embodiments, the content entry associated with a content item caninclude a URL flag indicating whether a URL to the content item has beencreated. For example, the URL flag can be a Boolean value initially setto 0 or false to indicate that a URL to the content item has not beencreated. Sharing module 130 can be configured to change the value of theflag to 1 or true after generating a URL to the content item.

In some embodiments, sharing module 130 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing module 130 can be configured to only return a content itemrequested by a generated link if the URL active flag is set to 1 ortrue. Thus, access to a content item for which a URL has been generatedcan be easily restricted by changing the value of the URL active flag.This allows a user to restrict access to the shared content item withouthaving to move the content item or delete the generated URL. Likewise,sharing module 130 can reactivate the URL by again changing the value ofthe URL active flag to 1 or true. A user can thus easily restore accessto the content item without the need to generate a new URL.

While content management system 106 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 106 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible.

FIG. 2 is a block diagram of an example system 200 for managing projectdata in a content management system. For example, system 200 cancorrespond to system 100 of FIG. 1, described above. As described above,system 200 can include content management system 106.

In some implementations, content management system 106 can includeproject module 202. For example, project module 202 can be a softwaremodule installed and/or running on content management system 106.Project module 202 can manage project folders and project dataassociated with projects. Project module 202 can generate a projectfolder view (e.g., graphical user interface) for presenting project datato a user (e.g., project member). Project module 202 can, for example,store content items and/or project data associated with a project inproject folder 204 in content storage 160.

In some implementations, content management system 106 can includecomments database 206. For example, comments database 206 can be storedin project folder 204 or stored separately from projects folder 204.Comments database 206 can store comments associated with a particularproject or many different projects. For example, project module 202 canread content items, including content item metadata, stored in projectfolder 204 and extract comments (e.g., messages from one user to anotheruser) from the content items. Project module can determine variousattributes (e.g., project identifier, author identifier, recipientidentifier, tags, source content item identifier, etc.) for eachcomment. Project module 202 can then store the comments in associationwith the determined attributes in comments database 206 so that projectmodule 202 can later locate comments based on the comment attributes.

In some implementations, project module 202 can analyze a comment todetermine attributes for the comment. For example, project module 202can determine a source content item attribute based on the content itemidentifier corresponding to the content item in which the comment wasfound. Similarly, project module 202 can determine a project identifierattribute for a comment based on the project folder where thecorresponding content item is stored. For example, when a user adds acomment to a content item stored in project folder 204 corresponding to“Project Widget”, then project module 202 can determine the projectattribute for the comment to be “Project Widget”.

Project module 202 can determine an author identifier for the commentbased on the user identifier associated with the user who wrote thecomment. For example, each user of content management system 106 can beassigned a user identifier. When a user edits a content item managed bycontent management system 106, content management system 106 can storemetadata for the content item that identifies the user who made thechanges to the content item and what changes (e.g., edits, comments,etc.) were made to the content item. Thus, project module 202 candetermine the author identifier attribute based on the user identifierstored in the content item metadata.

In some implementations, project module can determine comment attributesbased on special expressions included in a comment. For example, projectmodule 202 can analyze the comments to determine whether a commentincludes expressions (e.g., prefixes, tags, symbols, etc.) that indicateattributes for the comment. For example, content management system 106can define a user identifier prefix (e.g., the “at” symbol “@”) thatwhen added to a comment indicates a recipient identifier attribute willfollow. For example, a user can input a comment that includes “@kevin”to address the comment to a project member named Kevin. Thus, whenproject module 202 analyzes a comment and finds the string “@kevin”,project module 202 can determine that the recipient attribute for thecomment includes the user “Kevin.”

Similarly, content management system 106 can define a content itemprefix (e.g., the plus “+” character) that when added to a commentindicates a content item identifier attribute will follow. For example,a user can input a comment that includes “+overview.pdf” to create alink to a content item in the comment. When project module 202 analyzesa comment and finds the string “+overview.pdf”, project module 202 candetermine that a linked content item attribute for the comment includesthe content item “overview.pdf.” Project module 202 can, for example,convert a content item identifier prefixed with the content item prefixinto a link so that a user can access the content item through the linkembedded in the comment.

In some implementations, content management system 106 can define a tagprefix (e.g., the hash “#” character) that when added to a commentindicates a tag attribute will follow. For example, a user can input acomment that includes “#engineering” to tag the comment with a subject,classification, or some other information. When project module 202analyzes a comment and finds the string “#engineering”, project module202 can determine that a tag attribute for the comment includes the tag“engineering.” Project module 202 can, for example, use tags to organizecomments, tasks, or other project data, as described below.

In some implementations, content management system 106 can define a taskprefix (e.g., opening and closing square brackets “[ ]”) that when addedto the beginning of a comment indicates that the comment should beconverted into a task. For example, a user can input a comment thatincludes “[ ]” at the beginning of the comment to indicate that thecomment should be converted into a task. When project module 202analyzes a comment and finds the string “[ ]” followed by a commentand/or comment attributes, project module 202 can convert the commentinto a task. Project module 202 can treat the comment attributes as taskattributes and store the task and task attributes in task database 208in addition to or instead of storing the comment that generated the taskin comments database 206. For example, task database 208 can be storedin projects folder 204 or stored separately from project folder 204.

In some implementations, project module 202 can generate various projectfolder views based on the comments, tasks, and/or attributes stored incomments database 206 and/or tasks database 208. For example, projectmodule 202 can generate the graphical user interfaces described below byfiltering, sorting, aggregating, and/or otherwise organizing thecomments and/or tasks in comments database 206 and/or tasks database 208based on the comment attributes and/or task attributes, as described indetail below.

In some implementations, system 200 can include client device 240. Forexample, client device 240 can correspond to client device 102 _(i)described above. Client device 240 can, for example, be a laptopcomputer, tablet computer, smart phone, wearable device, and/or anyother computing device. Although FIG. 2 illustrates a system 200 havingonly one client device 240 (e.g., client device 102 _(n)), system 200can include many client devices 240 (e.g., client devices 102 _(i)-102_(n)) that interact with content management system 106 and/or projectmodule 202 to manage projects. For example, each member of a project mayhave a different client device 240 that communicates with contentmanagement system 106 to access project data managed by contentmanagement system 106 and/or project module 202.

In some implementations, client device 240 can include contentmanagement system (CMS) client 242. For example, CMS client 242 can be anative application of client device 240. For example, a native softwareapplication can be an application that is built specifically for thehardware and/or software configuration of client device 240. Thus, thegraphical user interfaces (and other functionality) of CMS client 242described below can be implemented using instructions, applicationprogramming interfaces (APIs), and other technologies native to clientdevice 240. To generate the various graphical user interfaces belowand/or implement various features described herein, CMS client 242 canrequest project data (e.g., project content items, project memberidentifiers, comments, tasks, etc.) from project module 202 over anetwork connection (e.g., through network 104). Project module 202 canobtain project data from project folder 204, comments database 206,and/or tasks database 208 and send the project data to CMS client 242.CMS client 242 can then present the project data on various graphicaluser interfaces generated by CMS client 242.

Alternatively, CMS client 242 can be a web client executed by a webbrowser running on client device 240. Thus, the graphical userinterfaces (and other functionality) of CMS client 240 can beimplemented using instructions, APIs, and other technologies that arenot native to client device 240. For example, CMS client 240 can bebuilt as a web application using non-native web code or instructions.CMS client 240 can be served to a web browser on client device 240 andthe web browser can execute CMS client 240 to present the graphical userinterfaces (and other functionality) to the user, as described in detailbelow. To generate the various graphical user interfaces below and/orimplement various features described herein, CMS client 242 (e.g., theweb browser) can request various project folder views (e.g., graphicaluser interfaces, web pages, etc.) from project module 202. Projectmodule 202 can generate the project folder views (e.g., the graphicaluser interfaces described below) for presenting project data (e.g.,project content items, project member identifiers, comments, tasks,etc.) and send the project views to CMS client 242 over a networkconnection (e.g., through network 104). For example, project module 202can obtain project data from project folder 204, comments database 206,and/or tasks database 208, generate the project folder views based onthe project data, and send the project folder views to CMS client 242.CMS client 242 can then present the project folder views on a display ofclient device 240.

In some implementations, client device 240 can include CMS daemon 244.For example, CMS daemon 244 can be a client of content management system106 that maintains synchronization of data between content managementsystem 106 and client device 240. For example, client device 240 caninclude managed content 250. Managed content 250 can be a portion of thefile system on client device 240 managed by content management system106 and/or CMS daemon 244. CMS daemon 244 and/or content managementsystem 106 can synchronize content items stored in managed content 250with content items stored in content storage 160. In particular, whenthe user of client device 240 is a member of a project corresponding toproject folder 204, CMS daemon 244 and/or content management system 106can synchronize project folder 204 and project folder 252 so thatproject folder 204 and project folder 252 include the same projectcontent items and/or project data (e.g., comments, tasks, etc.). Thus, auser of client device 240 can access project data stored in projectfolder 204/252 through CMS client 242 or through the local file system(e.g., project folder 252) on client device 240.

FIG. 3 illustrates an example graphical user interface 300 forpresenting project folders. For example, CMS client 242 can presentgraphical user interface (GUI) 300 on a display of client device 240. Insome implementations, GUI 300 can include side panel 301 presentingvarious graphical elements for viewing content management system dataassociated with a content management system user. While side panel 301is not represented in each figure described below, side panel 301 can bepresented along with each graphical user interface described herein. Inthe example illustrated by FIG. 3, the user has selected graphicalelement 302 to view content associated with a company that the userworks for and/or for which a business account has been established incontent management system 106. Upon receiving the selection of graphicalelement 302, CMS client 242 can present company folder view 303. Inother examples, the user can select other graphical elements to viewnon-business (e.g., personal) folders and/or non-business projectfolders.

In some implementations, folder view 303 can include project folders.For example, folder view 303 can present project folder 304 and/orproject folder 308. A user can cause content management system 106 tocreate a new project folder (e.g., project folder 304) by selectinggraphical element 314. Project folders 304 and/or 308 can be sharedfolders accessible by other users of content management system 106. Forexample, most projects include a team of people that perform varioustasks to accomplish the goals of the project. Thus, project folders 304and/or 308 can be shared with other users (e.g., project members) ofcontent management system 106. The members of each project can berepresented in areas 306 and/or 310 by graphical elements (e.g., images,initials, avatars, etc.). These project members can access projectfolders 304 and/or 308 respectively to view project content items andother project data for the projects corresponding to project folders 304and/or 308. A user can select a project folder to view details about thecorresponding project. For example, the user can select project folder304 (e.g., select a project) to cause CMS client 242 to present GUI 400of FIG. 4.

FIG. 4 illustrates an example graphical user interface 400 forpresenting a project folder view. For example, CMS client 242 canpresent GUI 400 on a display of client device 240 in response to theuser selecting project folder 304. GUI 400 can present project folderview 402 that presents various content items, comments, tasks, tagsand/or other project data. For example, a user can select graphicalelement 404 to cause CMS client 242 to present project data view 405that includes content items and/or folders associated with the selectedproject (e.g., “Project Widget”) in project folder view 402. Forexample, CMS client 242 can obtain the content item information and/orproject information presented in project data view 405 from projectfolder 204 through project module 202 or locally from project folder252, as described above.

In some implementations, project data view 405 can include projectconfiguration panel 406. For example, project configuration panel 406can include graphical representations 408 of project members. Graphicalrepresentations 408 can include photographs of members' faces, initials,avatars, and/or some other visual representation that users canrecognize to identify members of the selected project. In someimplementations, project configuration panel 406 can include graphicalelement 410 for adding new members to the project. For example, a user(e.g., project manager) can select graphical element 410 to cause CMSclient 242 to present graphical user interfaces for selecting and/oradding content management system users to the selected project.

In some implementations, project data view 405 can includerepresentations of folders within project folder 304. For example,project data view 405 can include graphical elements 414, 416 and/or 418representing various sub-folders of project folder 304. A user canselect a sub-folder (e.g., graphical element 414) to view content itemsstored in the selected sub-folder.

In some implementations, project data view 405 can include graphicalelement 420 for adding new content items to the project (e.g., projectfolder). In the description herein, the terms “project” and “projectfolder” can be used interchangeably since the project folder is arepresentation of a corresponding project and is used to contain,manage, and/or organize project data. For example, a user can selectgraphical element 420 to cause CMS client 242 to present GUI 500 of FIG.5 for adding a new content item to the project.

FIG. 5 illustrates an example graphical user interface 500 for adding anew content item to a project. For example, in response to receiving auser selection of graphical element 420, CMS client 242 can presentgraphical element 502 (e.g., a popup, a menu, etc.) on a display ofclient device 240.

In some implementations, graphical element 502 can present options foradding new content items to the selected project. For example, graphicalelement 502 can include graphical element 504 for uploading a file tothe selected project. A user can select graphical element 504 to causeCMS client 242 to present a file browser that allows the user to selecta content item to upload to the selected project folder managed bycontent management system 106. Graphical element 502 can includegraphical element 506 for creating a new folder in the selected project.A user can select graphical element 506 to cause CMS client 242 topresent a new folder dialog box that allows the user to create and namea new folder within the selected project folder managed by contentmanagement system 106. Graphical element 502 can include graphicalelements 508 and/or 510 for creating a new content item of a particulartype in the selected project. A user can select graphical element 508 or510 to cause CMS client 242 to present a new content item dialog boxthat allows the user to create and name a new content item of a specifictype within the selected project folder managed by content managementsystem 106. Graphical element 502 can include graphical element 512 foradding a link to a content item in the selected project. A user canselect graphical element 512 to cause CMS client 242 to present a dialogbox that allows the user to specify a link to a content item to add tothe selected project folder managed by content management system 106.After the user has added a new content item, folder, or link to theselected project folder, CMS client 242 can present the new contentitem, folder, or linked content item, as illustrated by FIG. 6.

FIG. 6 illustrates an example graphical user interface 600 forpresenting a view of a content item added to the selected projectfolder. For example, GUI 600 can be presented by CMS client 242 on adisplay of client device 240. GUI 600 can include graphical element 602for returning to a project folder view. For example, the user can selectgraphical element 602 to cause CMS client 242 to present GUI 400, GUI800, etc., on a display of client device 240.

In some implementations, GUI 600 can include content area 604. Forexample, content area 604 can present the content of a selected, newlyadded, or newly created content item in project folder 304. Content area604 can present a static preview (e.g., image) of content. Content area604 can provide an editor interface for editing or modifying the contentof the corresponding content item.

In some implementations, GUI 600 can include comments area 608 where auser can add or view comments on the content item. For example, the usercan select area 608 to invoke a text input area. The user can providetextual input to create a comment and the comment can be presented incomments area 608. For example, the user can create or view commententry 610. Comment entry 610 can include a graphical representation 612of the user who created comment entry 610. Comment entry 610 can includetextual comment data 614. In some implementations, the user can providetext input that includes special expressions or characters that can beinterpreted by CMS client 242 and/or project module 202. As describedabove, special characters can be input by the user to add a useridentifier or a content item identifier to the comment. Specialcharacters can be input by the user to create a task based on a comment,as described with reference to FIG. 7 below.

FIG. 7 illustrates an example text 700 that includes specialexpressions. For example, as the user provides text input to generatecomment 700, the user can type in special characters and/or specialexpressions that CMS client 242 and/or project module 202 can interpretto have special meaning. FIG. 7 illustrates how CMS client 242 and/orproject module 202 react to detecting special characters and/or specialexpressions in comments, content, tasks, or any other textual datamanaged by content management system 106.

As illustrated FIG. 7, the user has provided text input 710 and includedtask prefix 712 (e.g., ID at the beginning of text input 710. CMS client242 and/or project module 202 can interpret task prefix 712 as anindication that the user wishes text input 710 to be automaticallyconverted by CMS client 242 and/or project module 202 into a task forthe corresponding project.

Additionally, text input 710 includes user identifier prefix 714 (e.g.,“@”) followed by the first few characters of a user identifier. CMSclient 242 and/or project module 202 can interpret the identifier prefix714 as an indication that the user wishes to insert a user identifierinto text input 710. When CMS client 242 and/or project module 202detects user identifier prefix 714, CMS client 242 can presentsuggestion 716 including suggestions for content management system useridentifiers that match the characters that follow user identifier prefix714. In the example of FIG. 7, user identifier prefix 714 is followed bythe characters “Ke” and CMS client 242 has found a user identifier“Kevin Holm” that matches the characters “Ke.” CMS client 242 canpresent the user identifier “Kevin Holm” in suggestion 716 and the usercan select suggestion 716 to have the suggested user identifier added totext input 710. While FIG. 7 illustrates only one suggested useridentifier, CMS client 242 can present multiple user identifiers whenmultiple user identifiers match the sequence of characters followinguser identifier prefix 714.

In some implementations, the user can continue providing text input totext input 710 to generate text input 720. As illustrated by FIG. 7,after the user selects user identifier suggestion 716, user identifierprefix 714 can be removed (e.g., replaced) by the selected useridentifier 722.

Additionally, the user can provide text input for linking a content itemto text input 720. For example, the user can provide text input 720including a content item identifier prefix 724 (e.g., “+”) followed by afew characters of a content item identifier. When CMS client 242 and/orproject module 202 detects the content item identifier prefix 724, CMSclient 242 can present suggestion 726 including suggestions for contentitem identifiers that match the characters that follow content itemidentifier prefix 724. In the example of FIG. 7, content item identifierprefix 724 is followed by the characters “mo” and CMS client 242 hasfound the content item “Mockup.jpeg” that matches the characters “mo.”CMS client 242 can present the content item identifier “Mockup.jpeg” insuggestion 726 and the user can select suggestion 726 to cause CMSclient 242 to add a link to Mockup.jpeg to text input 720. While FIG. 7illustrates only one suggested content item, CMS client 242 can presentmultiple content items when multiple content item identifiers match thesequence of characters following content item identifier prefix 724.

In some implementations, the user can continue providing text input totext input 720 to generate text input 730. As illustrated by FIG. 7,after the user selects content item suggestion 724, CMS client 242 canreplace content item identifier prefix 714 with a link 732 to theselected content item 726.

Additionally, the user can provide text input for adding a tag to textinput 730. For example, the user can provide text input 730 including atag prefix 734 (e.g., “#”) followed by a few characters of a tag (e.g.,subject, classification, descriptive word or phrase, etc.).

When CMS client 242 detects that the user is finished with text input730 (e.g., the user submits the comment, closes the correspondingcontent item, a threshold period of time has elapsed since last input,etc.), CMS client 242 and/or project module 202 can process the comment(or text input) to determine the various attributes of the commentand/or to determine whether to convert the comment into a task. CMSclient 242 and/or project module 202 can then store the comment or taskand associated attributes (e.g., project identifier attribute, authoridentifier attribute, source content item attribute, recipient userattribute, linked content item attribute, tag attribute, etc.) in theappropriate database (e.g., comment database 206, task database 208).

FIG. 8 illustrates an example graphical user interface 800 presenting acontent item that was added to the selected project folder. For example,GUI 800 can be presented by CMS client 242 on a display of client device240 in response to the user selecting graphical element 602 of FIG. 6.In this example, the user has selected an option from graphical element502 to add a content item 802 to the selected project folder. Whencontent item 802 is added to the project folder, CMS client 242 and/orproject module 202 can read content item 802 and extract comments,tasks, tags, and other project data from the content item. CMS client242 can add the comments and tasks to comment database 206 and/or tasksdatabase 208, respectively, along with the corresponding attribute data,as described above.

FIG. 9 illustrates an example graphical user interface 900 forpresenting a description of the selected project. For example, the usercan select graphical element 902 to present an informational projectdata view 903 (e.g., Wiki page, overview, etc.) describing the project,project members, important documents, and/or other information. Projectdata view 903 can present a content item 904 (e.g., file, document, webpage, etc.) generated by one or more of the project members.

In some implementations, a project member can edit content item 904 fromwithin project data view 903 by providing textual input, addinggraphics, and/or other content. For example, a project member can editcontent item 904 by adding text to content item 904 and CMS client 242(or project module 202) can interpret special characters, patterns, orexpressions in the text as described with reference to FIG. 7. Forexample, a user who is editing content item 904 can provide string 906as input. String 906 can include the content item link prefix “+”followed by the characters “jou”. CMS client 242 can detect the contentitem link prefix and, in response to detecting the prefix, determinecontent items that have identifiers that include the charactersfollowing the prefix (e.g., “jou”). CMS client 242 can then present thedetermined content items as suggestions in graphical element 908 on GUI900. The user can select one of the suggested content items to cause CMSclient 242 to add a link to the content item in content item 904.

In some implementations, graphical element 908 can include a selectableitem for creating a new content item having an identifier that matchesthe characters that follow the content item prefix. When the userselects to create a new content item, CMS client 242 can insert a linkto the new content item in content item 904 presented in project dataview 903.

FIG. 10 illustrates an example graphical user interface 1000 forpresenting tasks associated with the selected project. For example, GUI1000 can be presented by CMS client 242 in response to receiving a userselection of graphical element 1002 presented in project folder view402. GUI 1000 can include, for example, project data view 1003 thatprovides a GUI for managing tasks associated with the currently selectedproject. For example, tasks can be created at the project level and/orthe content item level. Project data view 1003 can present tasksaccording to whether the task is a project level task or a content item(e.g., file) level task. For example, project level tasks can bepresented at the top of project data view 1003 and content item leveltasks can be presented below the project level tasks. Otherimplementations may reverse the order of presentation of the tasks. CMSclient 242 can obtain the task information presented in project dataview 1003 from task database 208 through project module 202, asdescribed above.

In some implementations, project data view 1003 can include graphicalelement 1004 and graphical element 1006 for creating a new project leveltask. For example, the user can select graphical element 1004 (e.g., atext input control) and enter text to describe a new project level task.The user can type text that includes the special characters, patterns,or expressions described above with reference to FIG. 7 to add links tocontent items, mention other users (e.g., project members) of contentmanagement system 106, and/or tag the new task. When other users arementioned in a task, project module 202 can assign the task to thementioned user, for example. When the user is done providing text inputto graphical element 1004, the user can select graphical element 1006(e.g., a button) to cause CMS client 242 and/or project module 202 tocreate the new project level task. When the project level task iscreated, project module 202 can store the project level task and taskattributes (as described above) in task database 208. For example, CMSclient 242 can send the description for the new project level task toproject module 202 so that project module 202 can determine theattributes of the task and store the task in task database 208.

In some implementations, project data view 1003 can present graphicalrepresentations of tasks associated with the selected project. Projectdata view 1003 can include task 1008. For example, task 1008 can be aproject level task created based on user input to graphical element 1004and graphical element 1006. Project data view 1003 can include tasks1010, 1012, and/or 1014. Tasks 1010, 1012, and/or 1014 can be contentlevel tasks created when a project member creates a task within or withreference to a project content item.

Each task 1008-1014 can include various attributes. For example, task1008 can include a task description. The task description can be atextual explanation of task 1008. Task 1008 can include recipientattribute 1020. For example, when a project member is at ‘@’ mentionedin a task, CMS client 242 and/or project module 202 can determine thatthe mentioned project member has been assigned the task. Task 1008 caninclude content item attribute 1022. For example, when a project contentitem is plus ‘+’ mentioned in a task, CMS client 242 and/or projectmodule 202 can create a link to the mentioned content item in the taskand determine that the mentioned content item is related to (e.g., is anattribute of) the task. Task 1008 can include tag attribute 1024. Whentask 1008 includes a tag prefix (e.g., ‘#’ character), CMS client 242and/or project module 202 can determine a tag attribute for the taskbased on the string that immediately follows the tag prefix. Task 1008can include author or creator attribute 1026. For example, CMS client242 can determine which project member created the corresponding task,as described above. Each content item task 1010, 1012, and/or 1014 caninclude text or other graphical representation of the content item fromwithin which the corresponding task was created. For example, contentitem tasks 1010, 1012, and/or 1014 can include source content itemattributes 1011, 1013 and/or 1015 respectively. For example,

Each of the tasks presented by project data view 1003 can be generatedby different project members and/or from within different projectcontent items or different project user interfaces. For example, task1004 can be generated from within project folder view 402 and/or projectdata view 1003 while task 1010 can be generated from within a projectcontent item (e.g., content item 802). As another example, task 1010 canbe generated from within a content item “Design.pdf” while task 1014 canbe generated from within content item “Schedule.url.” Task 1010 can begenerated by project member “Ben Berliner” while task 1012 was generatedby project member “Phil Bowman.”

In some implementations, a user can select a task to change the state ofthe selected task. For example, the user can select a checkboxassociated with a task to indicate that the task has been completed.When the user selects the checkbox, CMS client 242 can change the stateof the corresponding task to completed and remove the task from projectdata view 1003.

In some implementations, a user can select a task to modify attributesof the task. For example, the user can select the text description ofthe task to cause CMS client 242 to present a task editing graphicaluser interface (e.g., graphical element 1502 of FIG. 15). The user canprovide input to cause CMS client 242 to change various attributes ofthe selected task. CMS client 242 can then send the updated taskinformation to project module 202 for storage in task database 208 andpresent the updated task information in project data view 1003.

FIG. 11 illustrates an example graphical user interface 1100 forpresenting tagged project data. For example, GUI 1100 can be presentedby CMS client 242 in response to the user selecting graphical element1102 presented in project folder view 402. For example, in response toreceiving a user selection of graphical element 1102, CMS client 242 canpresent project data view 1103 that includes representations of taggedproject data. CMS client 242 can obtain the tagged project data fromcomments database 206, tasks database 208, and/or project folder 204through project module 202. Alternatively, CMS client 242 can obtain thetagged project data from local project folder 252 on client device 240.

In some implementations, project data view 1103 can present taggedproject data organized by tag. For example, a tag can be a stringpreceded (e.g., prefixed) by a special character or expression. Asdescribed above, the prefix for a tag can be the hash character ‘#’.Example tags can include “#engineering,” “#planning,” and/or “#design.”CMS client 242 can request tagged project data from project module 202.In response to the request, project module 202 can search commentsdatabase 206, tasks database 208, and/or project folder 204 for taggeddata (e.g., comments, tasks, content items, etc.) and generate acollection of tagged data. In some implementations, the collection oftagged data can be organized or sorted by tag. For example, all“#engineering” tags can be grouped together in the collection. All“#planning” tags can be grouped together in the collection.Alternatively, CMS client 242 can sort the tagged data upon receipt ofthe collection of tagged data from project module 202. After generatingthe collection of tagged data, project module 202 can send thecollection of tagged project data to CMS client 242 for presentation inproject data view 1103.

In some implementations, CMS client 242 can present the tagged projectdata organized into groups or sections according to the tags associatedwith the project data, as illustrated by FIG. 11. For example, projectdata view 1103 can present a group or section 1110 of “#engineering”tags that include tagged project data 1112 and/or 1114. CMS client 242can include project data 1112 and/or 1114 in section 1110 when CMSclient 242 determines that project data 1112 and/or 1114 includes the“#engineering” tag. Similarly, data view 1103 can present a group orsection 1120 of “#planning” tags that include tagged project data 1122.CMS client 242 can include project data 1122 in section 1120 when CMSclient 242 determines that project data 1122 includes the “#planning”tag.

In some implementations, project data view 1103 can include tagged dataof various types and/or from various project members. For example,project data view 1103 can include task 1112 and comment 114 that bothinclude the “#engineering” tag. Project data view 1103 can includecomment 114 created by project member “Ben Berliner” that includes the“#engineering” tag and task 1122 created by project member “Phil Bowman”that includes the “#planning” tag. Thus, project data view 1103 caninclude tags from across project content items, comments, tasks, and/orproject members.

FIG. 12 illustrates an example graphical user interface 1200 forpresenting comments associated with a project. For example, GUI 1200 canbe presented by CMS client 242 in response to the user selectinggraphical element 1202 presented in project folder view 402. Forexample, in response to receiving a user selection of graphical element1202, CMS client 242 can present project data view 1203 that includesrepresentations of comments associated with the selected project. CMSclient 242 can obtain the comments from comments database 206 throughproject module 202. Alternatively, CMS client 242 can obtain thecomments from local project folder 252 on client device 240.

In some implementations, project data view 1203 can include commentsassociated with various project content items. For example, project dataview 1203 can include comments 1210, 1212 and/or 1214. Comments 1210,1212 and/or 1214 can be presented, for example, ordered by when thecorresponding comment was generated or created. For example, if comment1210 is the most recent (e.g., newest) comment, comment 1210 can bepresented at the top of project data view 1203. Comments 1212 and 1214can be listed below comment 1210 in time order from newest to oldest. Insome implementations, comments can be presented in time order where thecomment at the bottom of project data view 1203 is the newest andincreasingly older comments are presented toward the top of project dataview 1203. Each comment 1210, 1212 and/or 1214 can include an identifier(e.g., graphical element 1216, text 1218) for author of the comment, anindication 1220 of when the comment was created, an identifier 1222 forthe content item in which the comment was created, and/or text 1224representing the comment.

FIG. 13 illustrates an example graphical user interface 1300 presentingrecently accessed content items. For example, GUI 1300 can be presentedby CMS client 242 in response to receiving user input selectinggraphical element 1302 presented in project data view 1303. To generateGUI project data view 1303, CMS client 242 can receive project data fromproject module 202 indicating times (e.g., timestamps) at which projectcontent items stored in project folder 204 were accessed (e.g., viewed,modified, created, moved, etc.). For example, the timestamps can bedetermined based on file system data and/or a change log that trackschanges to content items in the project folder. Since project folder 204is synchronized with project folder 252 on client device 240, thetimestamp associated with a content item may represent times at whichthe corresponding content item was accessed on client device 240.Alternatively, CMS client 242 can determine times (e.g., timestamps) atwhich project content items stored in project folder 252 were accessed(e.g., viewed, modified, created, moved, etc.). Since project folder 252is synchronized with project folder 204 on content management system106, the timestamp associated with a content item may represent times atwhich the corresponding content item was accessed on content managementsystem 106 or another client device similar to client device 240 (notshown) that has been synchronized with project.

In some implementations, project data view 1303 can include graphicalrepresentations of recently accessed project content items. For example,project data view 1303 can include graphical representation 1310 and/orgraphical representation 1320 of recently accessed project contentitems. For example, project data view 1303 can present time orderedrepresentations of recently accessed project content items. CMS client242 can, for example, generate project data view 1303 by presenting arepresentation of the most recently accessed project content item (e.g.,representation 1310) at the top of project data view 1303 and less andless recent project content items (e.g., representation 1320) in timeorder below the most recently accessed project content item. A user canscroll project data view 1303 upward to view content items that wereaccessed in the more distant past, for example.

Each content item representation (e.g., representation 1310,representation 1320, etc.) in project data view 1303 can present anidentifier (e.g., name, directory, path, etc.) for the correspondingproject content item. Each content item representation in project dataview 1303 can present an indication of when the corresponding projectcontent item was last accessed.

In some implementations, each content item representation in projectdata view 1303 can present a representation of the contents of thecorresponding project content item. For example, representation 1310 caninclude content representation 1312. Representation 1320 can includecontent representation 1322. For example, content representation1312/1322 can be a static preview image of the content of thecorresponding content item. Alternatively, content representation1312/1322 can be an editable or modifiable representation of thecorresponding content item. In some implementations, the user canprovide input to content representation 1312/1322 to scroll, zoom,print, or perform some other action with respect to the contentpresented in content representation 1312/1322. In some implementations,the user can select content representation 1312/1322 or correspondingcontent item identifier to open the corresponding content item in aneditor application for the selected content item.

FIG. 14 illustrates an example graphical user interface 1400 forpresenting tasks associated with a particular user of content managementsystem 106. For example, GUI 1400 can be presented by CMS client 242 ona display of client device 240 in response to the user selectinggraphical element 1404 from task menu 1402. For example, task menu 1402can be presented in side panel 301 on GUI 1400 and/or any of the othergraphical user interfaces described herein.

In some implementations, GUI 1400 can present user task view 1420. Forexample, user task view 1420 can present tasks associated with aspecific user. For example, if the user “Phil Bowman” (e.g., asindicated by graphical element 1414) is using client device 240 and/orCMS client 242 and has logged into content management system 106, usertask view 1420 can present tasks associated with (e.g., created by,assigned to, etc.) the user “Phil Bowman.” CMS client 242 can obtaintask information describing tasks associated with the user forpresentation in user task view 1420 from tasks database 208 throughproject module 202, for example. Alternatively, CMS client 242 canobtain task information describing tasks associated with the userlocally from managed content 250 on client device 240.

In some implementations, the tasks in user task view 1420 can bepresented in a list view as illustrated by GUI 1400 and indicated bygraphical element 1412. For example, user task view 1420 can presenttasks arranged or prioritized by due date. User task view 1420 canfilter tasks by due date. For example, user task view 1420 can presenttasks that are due within the next 7 days, 10 days, 2 weeks, etc. Usertask view 1420 can present tasks that are incomplete and/or in progress.

In some implementations, user task view 1420 can present tasks fromacross different projects. For example, when the user selects graphicalelement 1404, CMS client 242 can present tasks associated with the userand from various projects managed by content management system 106. Forexample, user task view 1420 can present tasks 1442 and 1444 associatedwith the particular user and from project 1440 (e.g., “Project Widget”).User task view 1420 can present tasks 1452 and 1454 associated with theparticular user and project 1450 (e.g., “Project Awesome”). User taskview 1420 can present task 1462 associated with the particular user andproject 1460 (e.g., “Project Opie”). As described above, the user canselect a task or task checkbox to change the state of the correspondingtask.

In some implementations, user task view 1420 can present tasksassociated with a particular project. For example, the user can selectgraphical element 1406 to cause user task view 1420 to filter tasks byproject. In other words, when graphical element 1406 is selected, usertask view 1420 can present tasks associated with a project associatedwith graphical element 1406 while hiding (e.g., not showing, filteringout, etc.) tasks associated with other projects. Thus, when CMS client242 receives a selection of graphical element 1406, CMS client 242 cangenerate and present user task view 1420 that includes tasks 1442 and1444 associated with project 1440 while hiding tasks 1452, 1454, and1462 associated with projects 1450 and 1460. Similarly, when CMS client242 receives a selection of graphical element 1408, CMS client 242 canpresent user task view 1420 that includes tasks associated with project1450 and hides tasks associated with project 1440 and 1460. When CMSclient 242 receives a selection of graphical element 1410, CMS client242 can present user task view 1420 that includes tasks associated withproject 1460 and hides tasks associated with project 1440 and 1450.

FIG. 15 illustrates an example graphical user interface 1500 forcreating a new task. For example, GUI 1500 can correspond to GUI 1400 ofFIG. 14. CMS client 242 can present GUI 1500 in response to the userselecting graphical element 1501 presented in user task view 1420, forexample. In response to receiving the user selection of graphicalelement 1501, CMS client 242 can present graphical element 1502 (e.g., awindow, a popup, a dialog box) on GUI 1500.

In some implementations, graphical element 1502 can include inputcontrols for defining a new task. The input controls can include textinput boxes, pull down menus, calendar controls, and/or other well-knownuser input controls. The text input controls can receive text inputincluding the special characters, expressions, prefixes, etc., describedabove with reference to FIG. 7 and CMS client 242 can interpret,translate, or convert the prefixed text into task attributes, asdescribed above. When the user provides text input into the textcontrols, CMS client 242 can present suggestions for users, projectmembers, content items, etc., based on the text input, as describedabove with reference to FIG. 7.

In some implementations, graphical element 1502 can include inputcontrol 1504 for describing the new task. For example, the user canprovide text input to input control 1504 to provide a title, subject,and/or description of the new task. Graphical element 1502 can includeinput control 1506 for associating the new task with a project. Forexample, the user can provide text input to input control 1506 toprovide an identifier for a project with which the new task isassociated. Graphical element 1502 can include input control 1508 forspecifying a due date for the new task. For example, the user canprovide text input to input control 1506 to specify a date when the taskis due for completion. Alternatively, input control 1506 can present acalendar representation that allows the user to select a due date fromthe calendar representation.

In some implementations, graphical element 1502 can include inputcontrol 1510 for assigning the task to a user of content managementsystem 106. For example, the user can provide text input to inputcontrol 1510 specifying the name of a user to whom the task is assigned.Graphical element 1502 can include input control 1512 for providingdetails about the task. For example, the user can provide text input toinput control 1512 to provide a summary description of the task,indicate related content items, indicate related users or projectmembers, and/or include tags or any other information relevant to thenew task. Graphical element 1502 can include input control 1514 forindicating a current state or status of the new task. For example, theuser can provide text input specifying the current status of the newtask. When input control 1514 is a pull down menu control, the user canselect the current status of the task from a set of predefined statuses(e.g., to do, in progress, completed, etc.). When the user is donedefining the task in graphical element 1502, the user can selectgraphical element 1516 (e.g., a button) to cause CMS client 242 to savethe new task in project folder 252 and/or in task database 208 throughproject module 202.

FIG. 16 illustrates an example graphical user interface 1600 presentinga newly created task. For example, GUI 1600 can correspond to GUI 1400of FIG. 14. CMS client 242 can present GUI 1600 in response to the userselecting graphical element 1516 to save a new task. For example, GUI1600 can present task 1602 associated with project 1460 as defined basedon the user input received by graphical element 1502.

FIG. 17 illustrates an example graphical user interface 1700 presentinga column view of tasks associated with the user. For example, CMS client242 can present a columnar representation of user task view 1420 inresponse to the user selecting graphical element 1704. The user can, forexample, switch between a list view and task view of user by selectinggraphical element 1412 (e.g., for list view) and/or graphical element1704 (e.g., for column view), respectively.

When presenting a column view of user tasks on user task view 1420, CMSclient 242 can present graphical elements 1710, 1720, and/or 1730representing respective task states. Each graphical element 1710, 1720,and/or 1730 can define an area (e.g., columns, rows, sections, etc.). Atask can be presented within the area of a graphical element 1710, 1720,and/or 1730 when the current state of the task corresponds to the taskstate represented by the corresponding graphical element 1710, 1720,and/or 1730. For example, graphical element 1710 can represent a “to do”state indicating that corresponding tasks 1712, and/or 1714 have not yetbeen started. Graphical element 1720 can represent a “in progress” stateindicating that corresponding task 1722 has been started but not yetcompleted. Graphical element 1730 can represent a “completed” stateindicating that corresponding task 1732 has been completed. Othergraphical elements may be presented representing other task states.

In some implementations, a user can provide input to user task view 1420to change the state of a task. For example, the user can select thecheckbox within task 1714 to indicate that task 1714 has been completed.Upon receiving the user input indicating that task 1714 has beencompleted, CMS client 242 can present a representation 1732 of task 1714that indicates that task 1714 has been completed within the area definedby graphical element 1730. For example, CMS client 242 can remove task1714 from graphical element 1710 and present task 1714 (now task 1732)within the area defined by graphical element 1730.

FIG. 18 illustrates an example graphical interface 1800 for changing thestate of a task. For example, GUI 1800 can correspond to GUI 1700 ofFIG. 17 described above.

In some implementations, a user can change the state of a task bydragging and dropping tasks into the areas defined by graphical elements1710, 1720, and/or 1730. For example, the user can select and drag task1802 from graphical element 1710 into graphical element 1720 to causeCMS client 242 to change the state of task 1802 from “to do” to “inprogress.” Similarly, the user can select and drag task 1804 fromgraphical element 1720 into graphical element 1730 to cause CMS client242 to change the state of task 1802 from “in progress” to “completed.”The user can select and drag task 1810 from graphical element 1710 intographical element 1730 to cause CMS client 242 to change the state oftask 1810 from “to do” to “completed,” as indicated by task 1730. Theuser can also provide input to change task states by moving tasks fromgraphical elements 1730 and/or 1720 to graphical elements 1710 and 1720,for example. When the user changes the state of a task, CMS client 242can send the updated task information, including the changed task state,to project module 202 for storage in task database 208 managed bycontent management system 106.

Example Processes

FIG. 19 is an example process 1900 for managing projects in a contentmanagement system. For example, process 1900 can be performed by CMSclient 242 and/or project module 202 to manage project data and presentgraphical user interfaces that allow a user (e.g., project member) toview and manage project data within a single project managementapplication and/or graphical user interface. The steps below aredescribed with reference to a computing device that performs operationsdescribed at each step. The computing device can correspond to a servercorresponding to content management system 106 and/or client device 240.The steps can be performed by project module 202 and/or CMS client 242.

At step 1902, a computing device can store a project foldercorresponding to a project. For example, the project folder can be ashared folder. The computing device can share the shared folder members(e.g., users) of the project who are collaborating on project tasks,content items, etc., to achieve a project goal. The computing device cancreate the project folder in response to receiving input from a user ofcontent management system 106 to create a new shared folder managed bycontent management system 106.

At step 1904, the computing device can store content items in theproject folder. For example, the computing device can store a contentitem in the project folder in response to a user uploading a contentitem to the project. The computing device can store a content item inthe project folder in response to a user creating a new content item inthe project or project folder view, as described above. The computingdevice can store a content item in the project folder in response to auser moving a content item into the project folder using standard filesystem operations. The computing device can store a content item in theproject folder in response to a user linking to or mentioning a contentitem in a comment, task, or other interaction with CMS client 242.

At step 1906, the computing device can store project data associatedwith the project. For example, the content items stored in the projectfolder can include comments, tasks, tags and other project data. Thecomputing device can read the content items to determine comments,tasks, and/or tags included in the project content items and store thecomments, tasks, and/or tags in project databases and/or the projectfolder, as described above. The computing device can store comments,tasks, and/or tag created externally to project content items. Forexample, the computing device can store comments, tasks, and/or tagscreated by a user in any of the graphical user interfaces describedabove.

At step 1908, the computing device can receive a user selection of aproject folder. For example, the user can select a project folder fromGUI 300 of FIG. 3.

At step 1910, the computing device can obtain project data associatedwith the project corresponding to the selected project folder. Forexample, the computing device can obtain project data (e.g., tasks,comments, tags, etc.) from various databases, described above. Thecomputing device can obtain the project data from the project folderstored on a server of content management system 106 or on client device240. The computing device can obtain the project data from withincontent items associated with the project and/or stored in the projectfolder.

At step 1912, the computing device can generate a project folder view.For example, in response to receiving the selection of the projectfolder and/or obtaining the project data, the computing device canpresent a project folder view that presents the project data asdescribed above with reference to the graphical user interfaces of FIG.4 to FIG. 13.

At step 1914, the computing device can cause a client device to presentthe project folder view. For example, when the computing device is aserver of content management system 106 and CMS client 242 is a webbrowser, the server can send a web page to CMS client 242 to cause CMSclient 242 to present the project folder view on a display of clientdevice 240. When the computing device is a server of content managementsystem 106 and CMS client 242 is a native browser, the server can send aproject data to CMS client 242 to cause CMS client 242 to present theproject folder view in a native GUI of CMS client 242 on a display ofclient device 240. Alternatively, CMS client 242 on client device 240can obtain project data from a local synchronized version of the projectfolder and present the project folder view based on the local projectdata.

FIG. 20 is an example process 2000 for managing tasks in contentmanagement system. For example, process 2000 can be performed by CMSclient 242 and/or project module 202 to manage user task data andpresent graphical user interfaces that allow a user (e.g., projectmember) to view and manage task data. The steps below are described withreference to a computing device that performs operations described ateach step. The computing device can correspond to a server correspondingto content management system 106 and/or client device 240. The steps canbe performed by project module 202 and/or CMS client 242, for example.

At step 2002, a computing device can store tasks associated with one ormore projects. For example, the computing device can store tasks in atask database, as described above. The computing device can store tasksin one or more project folders, as described above.

At step 2004, the computing device can receive a request for task dataassociated with a particular user. For example, project module 202 canreceive from CMS client 242 a request for task data associated with aparticular user.

At step 2006, the computing device can determine tasks associated withthe particular user. For example, project module 202 can search taskdatabase 208 for tasks assigned to and/or created by the particularuser.

At step 2008, the computing device can generate a user task view. Forexample, the user task view can include tasks associated with theparticular user, as determined at step 2006. The tasks can be organizedin a list view and/or grouped by project, as illustrated by FIG. 14 andFIG. 16. The tasks can be organized in a column view and/or grouped bytask state, as illustrated by FIG. 17 and FIG. 18.

At step 2010, the computing device can apply filters to tasks associatedwith the particular user. For example, step 2008 can be an optional stepthat applies project filters, time filters, and/or task state filters totasks associated with the particular user. For example, the computingdevice can apply a project filter based on a selected project such thattasks not associated with the selected project are filtered out of(e.g., hidden from) the user task view. The computing device can apply atime filter based on a configured amount of time (e.g., 7 days, 2 weeks,one month, etc.) such that tasks that have due dates that are not withinthe configured amount of time from the present time are filtered out of(e.g., hidden from) the user task view. The computing device can apply atask state filter that filters out tasks from the user task view thatare completed or are in some other state.

At step 2012, the computing device can cause a client device to presentthe user task view on a display of the client device. For example, whenthe computing device is a server of content management system 106 andCMS client 242 is a web browser, the server can send a web page to CMSclient 242 to cause CMS client 242 to present the user task view on adisplay of client device 240. When the computing device is a server ofcontent management system 106 and CMS client 242 is a native browser,the server can send user task data to CMS client 242 to cause CMS client242 to present the user task data in a native GUI of CMS client 242 on adisplay of client device 240. Alternatively, CMS client 242 on clientdevice 240 can obtain user task from managed content 250.

FIG. 21A and FIG. 21B show example possible system embodiments. The moreappropriate embodiment will be apparent to those of ordinary skill inthe art when practicing the present technology. Persons of ordinaryskill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 21A illustrates a conventional system bus computing systemarchitecture 2100 wherein the components of the system are in electricalcommunication with each other using a bus 2105. Example system 2100includes a processing unit (CPU or processor) 2110 and a system bus 2105that couples various system components including the system memory 2115,such as read only memory (ROM) 2120 and random access memory (RAM) 2125,to the processor 2110. The system 2100 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 2110. The system 2100 can copy data from thememory 2115 and/or the storage device 2130 to the cache 2112 for quickaccess by the processor 2110. In this way, the cache can provide aperformance boost that avoids processor 2110 delays while waiting fordata. These and other modules can control or be configured to controlthe processor 2110 to perform various actions. Other system memory 2115may be available for use as well. The memory 2115 can include multipledifferent types of memory with different performance characteristics.The processor 2110 can include any general purpose processor and ahardware module or software module, such as module 1 2132, module 22134, and module 3 2136 stored in storage device 2130, configured tocontrol the processor 2110 as well as a special-purpose processor wheresoftware instructions are incorporated into the actual processor design.The processor 2110 may essentially be a completely self-containedcomputing system, containing multiple cores or processors, a bus, memorycontroller, cache, etc. A multi-core processor may be symmetric orasymmetric.

To enable user interaction with the computing device 2100, an inputdevice 2145 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 2135 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 2100. The communications interface2140 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 2130 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 2125, read only memory (ROM) 2120, andhybrids thereof.

The storage device 2130 can include software modules 2132, 2134, 2136for controlling the processor 2110. Other hardware or software modulesare contemplated. The storage device 2130 can be connected to the systembus 2105. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 2110, bus 2105, display 2135, and soforth, to carry out the function.

FIG. 21B illustrates a computer system 2150 having a chipsetarchitecture that can be used in executing the described method andgenerating and displaying a graphical user interface (GUI). Computersystem 2150 is an example of computer hardware, software, and firmwarethat can be used to implement the disclosed technology. System 2150 caninclude a processor 2110, representative of any number of physicallyand/or logically distinct resources capable of executing software,firmware, and hardware configured to perform identified computations.Processor 2110 can communicate with a chipset 2160 that can controlinput to and output from processor 2110. In this example, chipset 2160outputs information to output 2165, such as a display, and can read andwrite information to storage device 2170, which can include magneticmedia, and solid state media, for example. Chipset 2160 can also readdata from and write data to RAM 2175. A bridge 2180 for interfacing witha variety of user interface components 2185 can be provided forinterfacing with chipset 2160. Such user interface components 2185 caninclude a keyboard, a microphone, touch detection and processingcircuitry, a pointing device, such as a mouse, and so on. In general,inputs to system 2150 can come from any of a variety of sources, machinegenerated and/or human generated.

Chipset 2160 can also interface with one or more communicationinterfaces 2190 that can have different physical interfaces. Suchcommunication interfaces can include interfaces for wired and wirelesslocal area networks, for broadband wireless networks, as well aspersonal area networks. Some applications of the methods for generating,displaying, and using the GUI disclosed herein can include receivingordered datasets over the physical interface or be generated by themachine itself by processor 2110 analyzing data stored in storage 2170or 2175. Further, the machine can receive inputs from a user via userinterface components 2185 and execute appropriate functions, such asbrowsing functions by interpreting these inputs using processor 2110.

It can be appreciated that example systems 2100 and 2150 can have morethan one processor 2110 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware modules, alone or in combination with other devices. In anembodiment, a software module can be software that resides in memory ofa client device and/or one or more servers of a content managementsystem and perform one or more functions when a processor executes thesoftware associated with the module. The memory can be a non-transitorycomputer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

What is claimed is:
 1. A method comprising: presenting, by a clientdevice, a graphical user interface comprising a project folder view, theproject folder view presenting project data corresponding to a projectmanaged by a content management system; receiving, by the client device,a user selection of a graphical element displayed via the graphical userinterface; responsive to receiving the user selection, requesting, bythe client device from the content management system, commentsassociated with content items associated with the project; receiving, bythe client device from the content management system, a first commentmade with respect to a first content item by a first user in theplurality of users and a second comment made with respect to a secondcontent item by a second user in the plurality of users; and presenting,by the client device, an updated project folder view that includes atleast a first representation of the first comment and a secondrepresentation of the second comment.
 2. The method of claim 1, whereinrequesting, by the client device from the content management system, thecomments associated with the content items associated with the project,comprises: requesting the comments from a remote database associatedwith the content management system.
 3. The method of claim 1, whereinrequesting, by the client device from the content management system, thecomments associated with the content items associated with the project,comprises: requesting the comments from a local project folder stored onthe client device.
 4. The method of claim 1, wherein presenting, by theclient device, the updated project folder view that includes the atleast the first representation of the first comment and the secondrepresentation of the second comment comprises: presenting a firstidentifier with the first representation, the first identifierindicating a first author associated with the first comment; andpresenting a second identifier with the second representation, thesecond identifier indicating a second author associated with the secondcomment.
 5. The method of claim 1, wherein presenting, by the clientdevice, the updated project folder view that includes the at least thefirst representation of the first comment and the second representationof the second comment comprises: presenting the first representation andthe second representation in time order from newest comment to oldestcomment.
 6. The method of claim 1, wherein the project folder viewincludes graphical elements selectable for accessing content items,comments, tasks, and tags associated with the project.
 7. The method ofclaim 1, wherein the first representation of the first comment includesa first content item identifier corresponding to the first content itemassociated with the first comment, and the second representation of thesecond comment includes a second content item identifier correspondingto the second content item associated with the second comment.
 8. Anon-transitory computer-readable medium including one or more sequencesof instructions that, when executed by one or more processors, causesthe processors to perform operations comprising: presenting, by a clientdevice, a graphical user interface comprising a project folder view, theproject folder view presenting project data corresponding to a projectmanaged by a content management system; receiving, by the client device,a user selection of a graphical element displayed via the graphical userinterface; responsive to receiving the user selection, requesting, bythe client device from the content management system, commentsassociated with content items associated with the project; receiving, bythe client device from the content management system, a first commentmade with respect to a first content item by a first user in theplurality of users and a second comment made with respect to a secondcontent item by a second user in the plurality of users; and presenting,by the client device, an updated project folder view that includes atleast a first representation of the first comment and a secondrepresentation of the second comment.
 9. The non-transitorycomputer-readable medium of claim 8, wherein requesting, by the clientdevice from the content management system, the comments associated withthe content items associated with the project, comprises: requesting thecomments from a remote database associated with the content managementsystem.
 10. The non-transitory computer-readable medium of claim 8,wherein requesting, by the client device from the content managementsystem, the comments associated with the content items associated withthe project, comprises: requesting the comments from a local projectfolder stored on the client device.
 11. The non-transitorycomputer-readable medium of claim 8, wherein presenting, by the clientdevice, the updated project folder view that includes the at least thefirst representation of the first comment and the second representationof the second comment comprises: presenting a first identifier with thefirst representation, the first identifier indicating a first authorassociated with the first comment; and presenting a second identifierwith the second representation, the second identifier indicating asecond author associated with the second comment.
 12. The non-transitorycomputer-readable medium of claim 8, wherein presenting, by the clientdevice, the updated project folder view that includes the at least thefirst representation of the first comment and the second representationof the second comment comprises: presenting the first representation andthe second representation in time order from newest comment to oldestcomment.
 13. The non-transitory computer-readable medium of claim 8,wherein the project folder view includes graphical elements selectablefor accessing content items, comments, tasks, and tags associated withthe project.
 14. The non-transitory computer-readable medium of claim 8,wherein the first representation of the first comment includes a firstcontent item identifier corresponding to the first content itemassociated with the first comment, and the second representation of thesecond comment includes a second content item identifier correspondingto the second content item associated with the second comment.
 15. Asystem comprising: one or more processors; and a non-transitorycomputer-readable medium including one or more sequences of instructionsthat, when executed by one or more processors, causes the processors toperform operations comprising: presenting a graphical user interfacecomprising a project folder view, the project folder view presentingproject data corresponding to a project managed by a content managementsystem; receiving a user selection of a graphical element displayed viathe graphical user interface; responsive to receiving the userselection, requesting, from the client device from the contentmanagement system, comments associated with content items associatedwith the project; receiving, from the content management system, a firstcomment made with respect to a first content item by a first user in theplurality of users and a second comment made with respect to a secondcontent item by a second user in the plurality of users; and presentingan updated project folder view that includes at least a firstrepresentation of the first comment and a second representation of thesecond comment.
 16. The system of claim 15, wherein requesting thecomments associated with the content items associated with the project,comprises: requesting the comments from a remote database associatedwith the content management system.
 17. The system of claim 15, whereinrequesting the comments associated with the content items associatedwith the project, comprises: requesting the comments from a localproject folder stored locally.
 18. The system of claim 15, whereinpresenting the updated project folder view that includes the at leastthe first representation of the first comment and the secondrepresentation of the second comment comprises: presenting a firstidentifier with the first representation, the first identifierindicating a first author associated with the first comment; andpresenting a second identifier with the second representation, thesecond identifier indicating a second author associated with the secondcomment.
 19. The system of claim 15, wherein presenting the updatedproject folder view that includes the at least the first representationof the first comment and the second representation of the second commentcomprises: presenting the first representation and the secondrepresentation in time order from newest comment to oldest comment. 20.The system of claim 15, wherein the project folder view includesgraphical elements selectable for accessing content items, comments,tasks, and tags associated with the project.